Conversation
Releases 1.0.1 and 1.0.2 contained a DLL and a few JSON files, which is not something anyone can start. Dropping the apphost dodged the Defender Wacatac.B!ml false positive but traded away the whole point of a release. Each platform now gets a self-contained, single-file build that runs on a machine with no .NET installed: TargetApiSimulator-<version>-win-x64.zip -> TargetApiSimulator.exe TargetApiSimulator-<version>-linux-x64.zip -> ./TargetApiSimulator TargetApiSimulator-<version>-osx-arm64.zip -> ./TargetApiSimulator TargetApiSimulator-<version>-portable.zip -> dotnet TargetApiSimulator.dll Console timestamps and the Microsoft.AspNetCore log filter move into code as defaults, so a standalone executable logs identically with no files beside it. Configuration still overrides both. Packages no longer carry web.config, aspnetcorev2_inprocess.dll or the static web assets manifest - IIS leftovers that made the download look unfinished. The pipeline guard is inverted: it now fails when a platform build produces no launcher, instead of failing when one is present. An unsigned binary may still be flagged. That is a signing problem, not a packaging one, and it applies equally to the version that could not be run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Releases 1.0.1 and 1.0.2 shipped a DLL and a handful of JSON files, which is not something anyone can start. Every platform now gets a self-contained, single-file executable that runs on a machine with no .NET installed.
Dropping the apphost in 1.0.1 dodged the Defender
Trojan:Script/Wacatac.B!mlfalse positive, but it traded away the whole point of a release. An unsigned binary may still be flagged — that is a signing problem, not a packaging one, and it applied equally to the build that could not be run.Release assets after this change
TargetApiSimulator-1.0.3-win-x64.zipTargetApiSimulator.exeTargetApiSimulator-1.0.3-linux-x64.zip./TargetApiSimulatorTargetApiSimulator-1.0.3-osx-arm64.zip./TargetApiSimulatorTargetApiSimulator-1.0.3-portable.zipdotnet TargetApiSimulator.dllThe three platform builds carry the .NET runtime inside the executable, which is where the 50 MB goes.
Contract impact
Packaging and startup defaults only. Console timestamps and the
Microsoft.AspNetCorelog filter move into code, so a standalone executable logs identically with noappsettings.jsonbeside it. Configuration still overrides both.Packages no longer carry
web.config,aspnetcorev2_inprocess.dllor the static web assets manifest — IIS leftovers that made the download look unfinished. The pipeline guard is inverted: it now fails when a platform build produces no launcher, instead of failing when one is present.Checklist
master, so it targetsmasterby designdotnet testpasses locally — 131 testsdotnet format --verify-no-changesis cleanVERSION.mdbumped to1.0.3andCHANGELOG.mdhas a[1.0.3]sectionHow to verify
Merging publishes v1.0.3. Then, from the release assets:
Expected:
200with bodytrue, and400with{"ErrorMessage": "This is not JSON"}for anything that is not JSON.